fix: bump RAM for listed-building - #90
Draft
tombrooks248 wants to merge 1 commit into
Draft
Conversation
tombrooks248
marked this pull request as ready for review
July 10, 2026 08:04
tombrooks248
force-pushed
the
fix/bump-listed-building-ram
branch
from
July 10, 2026 09:21
335b87c to
501fb65
Compare
tombrooks248
marked this pull request as draft
July 10, 2026 09:30
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this? (check all applicable)
Why has this not been implemented
On Friday the 10th this listed-building failed with the error described below, but after a rerun it actually ran cleanly. Given we are going to move these pipelines to pyspark soon, I've decided to drop this work for now, but keeping the PR in case we see this error again before pyspark can be implemented.
Description
Add a
memory: 65536(64 GiB) override to the listed-building / tree-preservation-orderbranch in
dag_triggers.py(both the scheduled and manual master DAGs).Why
listed-building-assemble-and-bakefailed overnight with a DuckDB out-of-memory error duringload_entities_range:These two collections already get a CPU bump (16 vCPU) via this branch, but memory stayed at the 32 GiB default, which is the Fargate minimum for 16 vCPU. DuckDB caps itself at 80% of container RAM (25.5 GiB) and hit that ceiling. Root cause is data growth (listed-building now ~387k entities)
Raising to 64 GiB gives DuckDB ~51 GiB usable (2× headroom). 16 vCPU permits up to 120 GiB
if we need to go further.
Which pipelines get affected
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
Please replace this line with instructions on how to test your changes, a note
on the devices and browsers this has been tested on, as well as any relevant
images for UI changes.
Added/updated tests?
We encourage you to keep the code coverage percentage at 80% and above. Please refer to the Digital Land Testing Guidance for more information.
[optional] Are there any post deployment tasks we need to perform?
[optional] Are there any dependencies on other PRs or Work?